Skip to content

[4.20.12] DFBUGS-6628: CVE bugs raised by PSRIT Team - 4.20 compat branch#2785

Open
avazeer wants to merge 2 commits into
red-hat-storage:release-4.20-compatibilityfrom
avazeer:cve_apr26_4_20_compat
Open

[4.20.12] DFBUGS-6628: CVE bugs raised by PSRIT Team - 4.20 compat branch#2785
avazeer wants to merge 2 commits into
red-hat-storage:release-4.20-compatibilityfrom
avazeer:cve_apr26_4_20_compat

Conversation

@avazeer
Copy link
Copy Markdown
Contributor

@avazeer avazeer commented May 10, 2026 •
edited by openshift-ci Bot
Loading

Fixes the following CVE bugs:
DFBUGS-6628,DFBUGS-6629,DFBUGS-6630,DFBUGS-6631,DFBUGS-6635,DFBUGS-6639,DFBUGS-6640,DFBUGS-6641,DFBUGS-6642,DFBUGS-6643,DFBUGS-6644,DFBUGS-6648,DFBUGS-6652,DFBUGS-6653, DFBUGS-6037, DFBUGS-5989, DFBUGS-6220, DFBUGS-6151

Fixed the following CVEs:
CVE-2025-12816,CVE-2025-13465,CVE-2025-15284,CVE-2025-66031,CVE-2025-68157,CVE-2025-68458,CVE-2025-69873,CVE-2026-22029,CVE-2026-25128,CVE-2026-25896,CVE-2026-26278,CVE-2026-26996,CVE-2026-27904,CVE-2026-27942,CVE-2026-29063,CVE-2026-33036

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 10, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: avazeer
Once this PR has been reviewed and has the lgtm label, please assign gowthamshanmugam for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@avazeer avazeer changed the title fixing cves filed by PSRIT team for 4.20 compat branch [4.20.12] DFBUGS-6628: CVE bugs raised by PSRIT Team - 4.20 compat branch May 14, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 14, 2026 •
edited by openshift-ci Bot
Loading

@avazeer: This pull request references [Jira Issue DFBUGS-6628](https://redhat.atlassian.net/browse/DFBUGS-6628), which is invalid:

  • expected the vulnerability to target the "odf-4.20.12" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Fixes the following CVE bugs:
DFBUGS-6628,DFBUGS-6629,DFBUGS-6630,DFBUGS-6631,DFBUGS-6635,DFBUGS-6639,DFBUGS-6640,DFBUGS-6641,DFBUGS-6642,DFBUGS-6643,DFBUGS-6644,DFBUGS-6648,DFBUGS-6652,DFBUGS-6653, DFBUGS-6037, DFBUGS-5989, DFBUGS-6220, DFBUGS-6151

Fixed the following CVEs:
CVE-2025-12816,CVE-2025-13465,CVE-2025-15284,CVE-2025-66031,CVE-2025-68157,CVE-2025-68458,CVE-2025-69873,CVE-2026-22029,CVE-2026-25128,CVE-2026-25896,CVE-2026-26278,CVE-2026-26996,CVE-2026-27904,CVE-2026-27942,CVE-2026-29063,CVE-2026-33036

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@avazeer
Copy link
Copy Markdown
Contributor Author

avazeer commented May 14, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 14, 2026 •
edited by openshift-ci Bot
Loading

@avazeer: This pull request references [Jira Issue DFBUGS-6628](https://redhat.atlassian.net/browse/DFBUGS-6628), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.20.12) matches configured target version for branch (odf-4.20.12)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@avazeer @openshift-ci-robot